T1_Architecture_and_State [ACTIVE v3.3].md

canon/tiers/01_Tier_1_Foundation/T1_Architecture_and_State [ACTIVE v3.3].md

T1\_Architecture\_and\_State

Humanity Project Living Architecture Map and Current State

Joshua Alexander Milks. CONFIDENTIAL.

Last updated: June 29, 2026\.

Current focus: Phase 6 Story Spine cascade preparation (foundation-hardening per docs/ROADMAP.md); Phases 5, 5.5, and 5.6 closed — T1\_Research\_Corpus\_Master v1.1 absorbing Ch 16-77 plus Prologue plus Epilogue against verified T1\_World\_Geography\_Master v2.3 region anchors. Chunks 1, 2, 3, 4A complete. Pre-Chunk-5A Cleanup Pass mid-execution: Sessions A through D complete covering CVD v1.4 lock plus T1\_WGM v2.3 lock plus T0 plus T1 doc version cascade plus T3\_Familiars\_Named plus T3\_Creatures\_Tameable ACTIVE v1.0 promotions; Session E Wave 4c plus Wave 5 active. Chunks 5A through 5C plus post-cascade absorption verification active post-Cleanup-close. Phase 5 closed at HUM-PHASE-5-COMPLETE marker Session 5M-6. Phase 5.5 Pre-Spine Cleanup follows at Phase 5.6 close — T2 ChapterDesign plus T2 ResearchBasis wholesale archive plus cascade-era memory cleanup. Phase 6 Story Spine cascade launches at Phase 5.5 close.

Active phase: Phase 5 Restructure of canonical document architecture against locked CVD foundation. Schema-first work order. Registry and document architecture is shaped backward from the build pipelines that consume canon, then forward through the projects that feed those pipelines, then into the Story Spine 02-77 cascade, then into book processing into the corpus database, then into region page building that further populates each registry and routes downstream pipeline consumers.

Doc Lifecycle and Authority Scope

Tier 1 Foundation. Living reference at \_source/01\_Tier\_1\_Foundation/ in the canon repo, which is the authoritative home post-migration. Sessions read it directly per CLAUDE.md routing; the Drive original is the frozen migration source.

Repo placement: \_source/01\_Tier\_1\_Foundation/T1\_Architecture\_and\_State \[ACTIVE v3.3\].md. Frozen Drive original under /Humanity/01\_Tier\_1\_Foundation/.

This doc owns the canonical document architecture map, the post-Phase-5 tier and registry rosters, current restructure state, downstream project status snapshots, recent architecture changes log, strategic roadmap forward to Phase 6 plus book processing plus region building, and immediate next actions. This doc does not own canonical content. Every roster entry is a pointer; the owner doc holds the substance.

Update cadence. The architecture map updates when canonical architecture shifts or migrations complete. The state and progress sections update at session close per Phase 5 cadence. The recent changes log appends per session and compacts on phase close.

Estimated stable size: 30 to 50 pages through Restructure close, then settling to monthly cadence through subsequent build phases.

Compaction Discipline

This doc records canonical architecture state, not session history. Session-by-session change entries accumulate in Recent Architecture Changes during phase execution because the work cadence demands per-session traceability. At each phase close, the section compacts: per-session entries roll up into one phase-close entry capturing canonical outcomes, deferred entries archive, superseded entries delete. Recent Architecture Changes never carries more than 6 to 8 active entries spanning the most recent two to three phase boundaries; older history archives to a separate phase-close summary doc or migrates into the relevant T1 doc's own Recent Changes section.

The same discipline applies to T1\_AaS body content. Session-related drift flags, in-flight pending decisions, transient operational notes, and version-skew tracking entries collapse at phase close into the canonical post-phase state. Body content stays at the canonical-architecture level — what exists, what owns what, what is authoritative. Session-state ephemera lives in T99 operational docs and Recent Architecture Changes during the session; it does not persist into canonical body content past phase close.

Compaction triggers at every phase close, recorded as a git commit plus phase tag per CLAUDE.md routing (replacing the HUM-PHASE-N-COMPLETE marker files). Phase 5M close triggers the first major compaction pass against the cumulative Phase 5 session entries. Subsequent phase closes trigger subsequent compactions. Phase close compaction is mandatory, not optional.

The same compaction discipline applies to session memory: per-session notes roll up at phase close into STATUS.md plus the auto-memory index per CLAUDE.md routing. The Drive-era userMemories store, its HUM-PHASE-N-SESSION breadcrumbs, and the 30-entry cap are retired.

Architectural Principles

Six principles govern the Humanity canonical doc architecture. They sit above the tier roster so future doc additions, splits, or migrations can be evaluated against the same criteria that produced the current structure.

Type A, B, C storage assignment. Every canonical doc and every section within a doc is classified A, B, or C. Classification determines storage format and consumer access pattern. The single-source-of-truth principle still applies; the dual format serves different consumers reading the same authority.

Type A is structured tables. Use when content is deterministically retrievable by ID or field value, when content feeds an executable AI pipeline like UE5, Meshy, or AIVA, when content must be exhaustively lookupable, when content changes frequently and must version-control cleanly, or when content relationships are graph-structured. Format is structured tables with row IDs, consistent schema, predictable field names, one row equal to one canonical fact. All Tier 0 registries are Type A. T1\_Trades\_Master quest gates table, T0\_Hard\_Lines, T0\_Character\_Index are examples.

Type B is prose. Use when content's meaning lives in voice, rhythm, implication, or emotional texture; when content is read by narrative-generating AI to preserve character voice; when structured form would destroy what makes it canonical; or when content is foundational interpretive material. Format is prose with section anchor IDs for retrieval-stable citation. T3\_Core\_Characters voice sections, T7\_Narrative\_Reference, T7\_Philosophy\_and\_Balance are examples.

Type C is hybrid header plus body. Use when content has both executable structured aspects and irreducible narrative voice, or when multiple AI consumers read the same doc but need different data shapes. Format is machine-readable header block, then a hard separator (HEADER END — BODY BELOW), then prose body with section anchors. Header carries doc metadata, authoritative-for domains, defers-to references, requires-loading dependencies, content-specific structured fields. Body carries narrative prose. Hard no-overlap rule: facts in header do not repeat in body as prose; body builds on header. T2 chapter canon docs, T4\_House\_of\_Velheim\_Canonical, T5 questline detailed docs, T6 weapon detailed docs are examples.

Consumer access pattern by type. Narrative consumers stop after the separator and read body. Validation and build consumers stop at the separator and read header. Hybrid consumers read both. The separator is unambiguous and machine-detectable so parsers split header from body reliably.

Document Authority Hierarchy

When canonical docs conflict, resolve by this hierarchy. Higher authority wins.

Conflict protocol. When a session finds conflicting content across canonical docs, identify the authoritative doc per this hierarchy, use its version, log the conflict in the Recent Architecture Changes section for resolution, and never silently pick a version.

Tier 0 Registry Architecture

Tier 0 is the structured-data layer. Thirty registries total at canonical folder ID 1ni2qIY44X47qZ26fxPCU7lF2RL6AEJPZ: twenty-nine Google Sheets registries plus one canonical schema-authority Google Doc (T0\_Schema\_Dictionary). Canonical per-registry schema authority lives at T0\_Schema\_Dictionary ACTIVE v1.3.

Two adjacent thread artifacts handle different cuts of thread canon. T0\_Thread\_Grid is the per-chapter occurrence map (22 by 79 cell matrix, anchor-stage classified). T0\_Thread\_Registry is the per-thread summary catalog (22 row metadata card). Both are needed; neither replaces the other.

Active populate registries (21 sheets plus Schema Dictionary doc)

Per Schema Dictionary §3.1 through §3.21. Schema Dictionary §3.1 documents the dictionary itself as a Google Doc rather than a sheet; the doc-type exception is canonical.

Scope-locked registries (6)

Per Schema Dictionary §4.1 through §4.6. Schema authority documented at minimum-viable scope; full column rosters lock at per-registry populate session.

Newly spun registries (2)

Per Schema Dictionary §5.1 through §5.2. Headers locked on minimum-viable principle. Column expansion derived from region page build feedback per pipeline-driven schema principle.

Removed in Phase 5M-prep triage (4)

Folder-policy implicit-archive applied. Absent from 00\_Tier\_0\_Master\_Indices folder.

Tier 1 Foundation Architecture

Tier 1 holds the prose canonical foundation. Twenty docs in current Drive folder state at canonical folder ID 1y7MSWfLW4bxxLDFbR9uley6-FBvQPyJ4.

Foundation docs at ACTIVE state (13)

Foundation docs at ACTIVE single-section state (1)

Foundation docs at DRAFT state (4)

Foundation docs promoted to ACTIVE post-migration (1)

This Architecture doc (1)

Pre-restructure docs retiring at Phase 5M close (3)

Folder-policy implicit-archive applied at Session 5M-4. All three absent from 01\_Tier\_1\_Foundation folder. Absorption-verify audit pass complete across all sections per outputs/5M-4\_Audit\_Findings.md.

T1 placeholders removed at 5M-4 (2)

Folder-policy implicit-archive applied. Both absent from 01\_Tier\_1\_Foundation folder.

T1 retirement at 5M-5 Phase A (1)

Folder-policy implicit-archive applied at 5M-5 Phase A. Absent from 01\_Tier\_1\_Foundation folder.

Tier 2 Chapter Canon Architecture

Tier 2 holds transitional per-chapter design and research basis docs at canonical folder ID 1P2MCMvxXxni0dqwsXMSSHvy3JSKe5Oky. Status TRANSITIONAL per pre-restructure migration model; full retirement deferred to post-Phase-5.6 plus T1\_Research\_Corpus\_Master v1.1 completion per Josh Session 5M-4 directive. Cascade-era content; not read by Phase 6 Spine v2.4 cascade authoring which routes against CVD v1.4 plus T1 reference plus T0 registries.

Twelve docs total at current Drive state. All DRAFT v0.1, six ChapterDesign plus six ResearchBasis covering Ch 02 through Ch 77 in five chapter-range chunks plus a sixth covering Ch 66-77.

Retirement scheduled. Phase 5.5 Pre-Spine Cleanup wholesale archives T2\_ChapterDesign plus T2\_ResearchBasis per folder-policy implicit-archive once Phase 5.6 Corpus Doc Rebuild plus T1\_Research\_Corpus\_Master v1.1 absorption complete. Until then T2 docs serve as cascade-era forensic reference. Phase 6 cascade does not read T2 content as authoritative.

Phase 5.5 executed 2026-06-29: all 12 T2 ChapterDesign plus ResearchBasis stubs (empty 47-byte title-only files, no chapter body) deleted from the repo and the Tier 2 folder removed. Tier 2 retirement complete; the Phase 6 Spine v2.4 cascade reads CVD plus T1 reference plus T0 registries, never T2\.

Tier 3 Character Canon Architecture

Tier 3 holds character canon at canonical folder ID 1RHOD3uYcl48Vd2N\_5c1QIbndbCAjt0J4. Four docs covering core characters, supporting characters, named familiars, and tameable creatures. Type B prose at canonical reference voice per Type A B C storage assignment — third-person canonical description at canon-reference authority, distinct from close-third protagonist voice owned by T1\_Story\_Spine.

Two ACTIVE plus two DRAFT at current Drive state. Core plus Supporting locked at Phase 5K. Familiars Named plus Creatures Tameable populate post-Phase-6 alongside region page build feedback.

Tier 4 Antagonist Canon Architecture

Tier 4 holds antagonist family canon at canonical folder ID 1X8z7BgA5UQVgs9qLBImUiaPWla1tc-hj. Single doc constituting the full Tier 4 roster. Type C hybrid storage per Type A B C assignment — structured per-chapter operational catalog at §7 through §9 alongside prose family-level canon at §1 through §6 plus §10 through §11.

Tier 5 Questline Canon Architecture

Tier 5 holds questline canon at canonical folder ID 1lYzfx7PDpjoQVkhkNzKjMjBDgVdbFkLJ. Summary-plus-detail layering per Architectural Principles — one summary doc provides navigation across 23 questlines (Main Story plus 10 Trade plus 12 Side), nine detailed docs hold per-questline content. Most project sessions load only the summary; detailed docs load only when a session is actively working on that specific questline.

Ten docs total, all DRAFT v0.1 at current Drive state. Populate at Phase 6 plus Phase 4B Quest Writing pipeline.

Tier 6 Weapons Canon Architecture

Tier 6 holds weapons canon at canonical folder ID 1rc0oa7pkB9RfHeqAdk8gaae23EuA5dEb. Summary-plus-detail layering — one Master Index doc plus two per-category detailed docs covering 72-weapon framework split 36 Brute plus 36 Trickery/Sorcery per T1\_Combat\_System\_Spec v1.0.

Three docs total, all DRAFT v0.1 at current Drive state. Populate at Phase 6 alongside region build feedback and at Phase 4 quest writing for legendary-weapon unlock questlines.

Tier 7 Production Canon Architecture

Tier 7 holds production canon at canonical folder ID 1WbuA9KYWUhyM21XEz63gfueN--DgyJrQ. Three docs covering project-level reference materials, narrative reference content, and philosophy plus balance canon. Type B prose per Type A B C storage assignment — narrative-generating Claude sessions read these for character voice and balance philosophy guidance.

All three DRAFT v0.1 at current Drive state. Production refinement at Phase 6 alongside region build feedback.

T1\_Ability\_Tree previously lived at Tier 7 (T7\_Ability\_Tree) per Session 5G-pre lock. Promoted to Tier 1 Foundation at Session 5G arc complete per Phase 5 plan T1 promotion. Listed at Tier 1 Foundation Architecture section above.

Tier 8 Region Pages Architecture

Tier 8 holds region pages at canonical folder ID 1Eu1V\_f4EH6hYw7P6VL-\_dC7Dt70CdXqn. Empty pre-Phase-6. 69 region pages populate at Phase 6 region page build pace of one region per weekend, Flores Island first per T1\_Build\_Pipeline\_Contracts §7 Region Page Build pipeline plus T1\_Region\_Page\_Template v1.0 canonical 20-section spec.

Each T8 region page instantiates the T1\_Region\_Page\_Template 20-section structure. Region pages are the primary canonical output for all downstream pipeline consumers — UE5, Meshy, AIVA, ElevenLabs, Cinematic, Quest Writing, Book Processing, SFX. Region page authoring at Phase 6 surfaces pipeline consumer demand which routes into T0 registry column expansions per pipeline-driven schema principle.

T8 region pages use the Knowledge Base pattern per AI Consumer Analysis — semantic search over large region detail rather than full-load. Region detail loads on demand when a session is actively working on that specific region.

Tier 97 Concept Art Architecture

Tier 97 holds concept art reference materials at canonical folder ID 1SYL4WE8TbpQsPe4eispmwqszxqil\_Ksn. Empty at current state. Populate at Phase 6 region build alongside Meshy mesh generation plus Project 7 Art production. Concept-art reference layer per T1\_Build\_Pipeline\_Contracts §1.7 NeoStack tool surface and §2 Meshy pipeline.

Tier 98 Legal Architecture

Tier 98 holds legal documents at canonical folder ID 1IE8Z7705aHUO1ftCHlMoxIS9AjBXesZG. Empty at current state. Populate target spans crowdfunding launch (compositional copyright registration, ElevenLabs voice clone authorization per §4.4.1, MMO terms of service, partner contracts). Legal scope tracked separately from world canon — Tier 98 isolates legal artifacts from canonical content read by AI build pipelines.

Tier 99 Operational Architecture

Tier 99 holds operational guidance distinct from world canon at canonical folder ID 1lpXIPgXC5EusGYj-M2cv91B7cf6BsaNy. Ten docs in current Drive folder state plus one working-files subfolder.

T99 docs at ACTIVE state (7)

T99 docs at DRAFT state (1)

T99 transitional docs retiring at HUM-PHASE-5-COMPLETE (2)

Operational scope tied to Phase 5 execution. Folder-policy implicit-archive applies at Phase 5 close marker file.

T99 working-files subfolder (1)

Tier 99 docs hold operational authority on workflow and protocol. Canonical world content lives in Tier 0 and Tier 1\.

Per-Project File Loading

Per-project canonical file load specifications finalize at Phase 5 close after all T1 docs are refined and all T0 registries are populated. The current target shape carries forward from the pre-restructure 14-to-18 file range per project, sized within Pro plan limits with comfortable headroom on Max plans.

T1\_Architecture\_and\_State is read on demand from the repo. CLAUDE.md routing plus per-skill load manifests replace per-project custom instructions.

Concept-level project loads. Specific file lists ratify at Phase 5 close.

AI Consumer Analysis

The canonical knowledge base is a database for AI consumers. Every architecture decision serves one or more of the consumer types below. Content takes the shape its consumers need.

Twelve consumer types operate across the canonical base.

Consumer-type storage implications. Narrative consumers need Type B prose intact; character voice cannot be reduced to fields. Validation consumers need Type A structured retrieval with deterministic lookup. Build consumers need Type A exclusively with schema version pinning and extensibility fields. Processing consumers need Tier 0 as routing layer with append-only writes under normalization gates.

Three-level loading applied to Tier 0\. Level 1 metadata is always loaded at roughly 5 to 10 percent of session context: registry headers plus high-frequency lookup tables. Level 2 body loads on trigger at roughly 5 to 10 percent when activated: full registry body for the registry relevant to the query. Level 3 external-file access carries zero context cost: large detail blobs accessed via tool, not loaded into context.

Drive Folder Structure

Canonical project root at /Humanity/ at gdrive folder ID 1MY3lC93P0KgO9ygqC1ofbpjYTGmAd\_bt. Twelve canonical tier and operational folders plus one archive subtree live directly under the project root. Working files for projects route through their tier folders (T1 through T8) rather than separate project folders; pre-restructure working folders survive inside the archive subtree for forensic reference only.

Per-tier canonical folder IDs locked at Session 5M-5 Phase B folder-scoped verification.

Archive subtree at /Humanity/\_Archive/ holds the pre-restructure project working folder structure preserved for forensic reference. Contents include 00\_Foundation (pre-restructure foundation docs at folder ID 1-mO4fZuaWsAHN9ilzQFNB48ohuu-qQlx), 01\_Book\_Research (canonical source-material reference library at folder ID 1km\_kZuLJdYvpUvc7eAnUgNkAH6lQsy0S — the substrate the T1\_Research\_Corpus\_Master plus T0\_Source\_Material\_Registry plus T0\_Research\_Corpus\_Registry route to), 02\_Region\_Pages at folder ID 18wTPmaEW5\_rwJg6-Ql8eIH2P1zsv9HLD, 03\_Chapter\_Design\_Briefs at folder ID 1ukEeC5jxREqRYyi\_EitymMIVoV4dZxya, 04\_Quest\_Content at folder ID 1KJ8nPGgvz\_JtwtWOOZp168aTtPHGIIPK, 05\_UE5\_Code at folder ID 1mJQIy9\_EJiAWDu\_vO9mbRU-84qjxCxOV, 06\_Music at folder ID 1NfycAsBJQhGPCzQ2nIe\_Z\_QuKL7uorLL, 07\_Art at folder ID 1Zls5Hnu2a29VyFjo37OAWIOFFwwPmC74, 98\_MASTER\_FILES at folder ID 1Z-63CM4XMkvzjmijvv2NXJw1v7fffd85, and \_Archive\_2026\_04\_Restructure at folder ID 1CXIXkFLLcF2Z9ew4MkVN6K-pt9MxfVMx (Restructure-era archived placeholder docs and superseded versions). The Books folder at folder ID 1-iiIga-I0rHz\_m4pERGFWcyRiu3fitXU is a cross-project source library that pre-dates the Humanity restructure.

Source material reference. The canonical reference library lives at /Humanity/\_Archive/01\_Book\_Research/ at folder ID 1km\_kZuLJdYvpUvc7eAnUgNkAH6lQsy0S. Local source-text routing per T1\_Research\_Corpus\_Master now follows docs/BOOK\_ACQUISITION.md — deep-research synthesis is the default substrate path and the curated MUST-ACQUIRE set covers physical buys; the retired Windows-side Drive-mount path (G:\\My Drive\\HUMANITY\\01\_Book\_Research\\A\_Source\_Texts) is not mounted on the build machine. Book Processing pipeline §8 plus T1\_Research\_Corpus\_Master plus T0\_Source\_Material\_Registry plus T0\_Research\_Corpus\_Registry all route here for canonical source-text reference.

Folder-policy retirement discipline. Adopted at Session 5M-4 close. Folder structure under /Humanity/ is canonical state going forward. Absent from canonical folder equals implicit-archive. No rename ceremony or per-doc title-rev required for retiring artifacts. Supersedes the per-doc \[ARCHIVED v.X.X\] title-rev approach proposed in T99\_Phase\_5\_Closing\_Sequence\_Handoff §5.4. Git repo state (working tree plus commit history) is the authoritative state check per CLAUDE.md routing; folder-scoped Drive search at the canonical folder IDs above applies only to the frozen migration source; documents in /\_Archive/ or /\_Archive/\_Archive\_2026\_04\_Restructure/ are implicit-archived regardless of title status.

Doc Naming Convention

Format. \[TIER\_PREFIX\]\_\[DOC\_NAME\] \[STATUS vVERSION\].gdoc

Components. TIER\_PREFIX is one of T0, T1, T2, T3, T4, T5, T6, T7, T8, T99. DOC\_NAME is descriptive, underscored, with no spaces. STATUS is one of ACTIVE, DRAFT, ARCHIVED, SUPERSEDED, DEPRECATED. VERSION is vMAJOR.MINOR (for example v1.0, v2.1).

Rules.

Status Definitions and Transition Rules

Transition rules. DRAFT to ACTIVE on normalization pass success and filing to canonical folder. ACTIVE v1.0 to ARCHIVED v1.0 when ACTIVE v2.0 lands for the same base name. ACTIVE to SUPERSEDED when architecture change makes the doc obsolete rather than revised. ACTIVE to DEPRECATED only with mandatory retirement date in the title. Folder-policy implicit-archive supersedes title-rev where the doc has moved out of canonical folder.

One ACTIVE per logical base name, period. All previous versions archived with version preserved.

Uniqueness Enforcement and Transitional Doc Handling

Every session filing a doc checks three things. First, whether the filename ACTIVE already exists, in which case this is a revision and the previous ACTIVE must transition to ARCHIVED. Second, whether the filename DRAFT already exists, in which case this is continuation and a second draft is not created. Third, whether the base name is used anywhere including archive, to verify no collision. Normalization pass validates this before admission.

Transitional docs that survive the Restructure carry either folder-policy retirement at phase close marker or mandatory retirement date in the title. T99\_Phase\_5\_Closing\_Sequence\_Handoff plus T99\_Pipeline\_Contract\_Buildability\_Audit retire at HUM-PHASE-5-COMPLETE marker via folder-policy. T99\_Story\_Spine\_Build\_Logic v3.0 retires at HUM-STORY-SPINE-COMPLETE marker at Phase 6 close.

Phase 5 Restructure Progress

Phase 5 sequence: Surviving T1 Seed Content refines, NEW T1 spec doc populates, T0 registry populates, absorbed-doc retirements, Phase 5 closing audit. Twenty-five sessions across four work streams.

Sessions complete (25)

Twenty-five sessions executed across four work streams. T1 refinement and authoring stream, T0 registry population stream, absorbed-doc retirement stream, Phase 5 closing audit stream.

T1 stream. Session 5B Threads\_22\_Master\_References v2.0. Session 5C World\_Geography\_Master v2.0. Session 5D Languages\_and\_Script\_Master v2.0 plus Inscription\_Spine scratchpad. Session 5E Vril\_and\_Magic\_System\_Master v2.0 plus Vril\_Site\_Registry 29-row scratchpad plus Component 11 9-anchor catalog lock per CVD v1.1 §19.1. Session 5F Integrity\_Paths\_Worldstates\_Master v2.0 plus CVD §9.2 five-band canonical refresh plus Worldstate\_Variables 25-row populate. Session 5G arc (5G, 5G-2, 5G-4-A through 5G-4-D-3) Ability\_Tree v1.4 ACTIVE Final Lock at 185 abilities promoted T7 to T1 plus Ability\_Tree\_Registry v1.4 185-row populate. Session 5H Combat\_System\_Spec v1.0 72-weapon framework plus 5 chapter-level Boss anchors. Session 5I Trades\_Master v1.0 twelve-tier quest gate framework plus Trade\_Registry 10-row populate. Session 5J Tier\_C\_MMO\_Spec v1.0 three-tier architecture canon. Session 5K-1 Core\_Characters v1.0 plus Character\_Index CH\_0001-CH\_0007 rows. Session 5K-2 Supporting\_Characters v1.0 plus Character\_Index CH\_0008-CH\_0118 rows. Session 5K-3 House\_of\_Velheim\_Canonical v1.0 plus Antagonist\_Network\_Registry 62-row populate. Session 5L-3 World\_Geography\_Master v2.1 plus Integrity\_Paths\_Worldstates\_Master v2.1 companion-doc extensions. Session 5M-5 Phase A RNG\_Sigma\_Constraint\_System v1.0 body populate plus T1\_Tier\_B\_DLC\_Catalog plus T1\_Personal\_Dimension\_Spec demotes to DRAFT v0.1. HUM-T1-RCM-V1-COMPLETE May 16 Research\_Corpus\_Master v1.0 at 117K covering 26 H2 sections Ch 2-15.

T0 stream. Session 5A initial four-sheet schema lock (Chapter\_Index, Region\_Index, Thread\_Grid, Character\_Index headers). Session 5B-2 Thread\_Grid 644-cell population. Session 5C-2 Chapter\_Index v1.1 33-column 79-row populate. Session 5D Language\_Script\_Registry 73-row scratchpad. Session 5L close Hard\_Lines 120-row TSV. Session 5M-1 Schema\_Dictionary v1.0 ACTIVE lock for 24 in-scope registries. Session 5M-2 Schema\_Dictionary v1.1 ACTIVE lock absorbing 5 spawned-by-pipeline registries plus §2.7 entity\_id format framing patch. Session 5M-3 five-sheet creation at Tier\_0 (Theme\_Registry 12r, Voice\_Registry 10r, Scene\_Spec\_Registry 16r, Quest\_Definition\_Registry 16r, Source\_Material\_Registry 5r).

Absorbed-doc retirement stream. Session 5L Distribution Blueprint v4.1 retired by canonical distribution plus Region\_Page\_Template ACTIVE v1.0 created. Session 5L-2 Build\_Pipeline\_Contracts v0.1 to v1.0 all 10 pipelines locked. Session 5M-prep memory consolidation pass plus T1\_AaS sync v2.0 to v2.2. Session 5M-4 absorbed-doc retirement audit pass complete under folder-policy retirement model — T1\_GDD\_Core plus T1\_GDD\_Systems plus T1\_Research\_Depth\_Standards plus T1\_Enhancement\_Pillars plus T1\_Grimoire\_System\_Spec plus four T0 placeholders plus T99\_Restructure\_Blueprint v4.1 retired by folder-policy.

Phase 5 closing audit stream. Session 5M-5 Phase B T1\_Architecture\_and\_State full rewrite v2.2 to v3.0 with full tier inventory completeness. Session 5M-5 Phase C v4.2-Phase-5-Close custom instructions authoring. Session 5M-5 Phase D drift resolution batch (seven items closed, three routed forward, T0\_Source\_Material\_Registry retention confirmed). Session 5M-5 Phase E memory cleanup batch including cn0 to nu0 ID drift fix. Session 5M-5 Phase F T0 sheet population landings (CHAR\_NNNN rename, Nan Madol migration, Schema\_Dict v1.2 patches, CI Registry v1.0 entries). Session 5M-5 Phase G collapsed (audit doc trashed as duplicate ledger). Session 5M-6 HUM-PHASE-5-COMPLETE marker file landed plus this Architecture doc compaction pass v3.0 to v3.1 plus userMemories rollup plus T99 transitionals retirement surfaced.

Phase 5 exit

HUM-PHASE-5-COMPLETE marker landed May 17, 2026, Session 5M-6. Gates Phase 5.5 Pre-Spine Cleanup launch plus v5-Operational custom instructions activation. v4.2-Phase-5-Close custom instructions retire at this marker. Phase 5 sequence closed.

Strategic Roadmap

Forward sequence from Phase 5 close through book processing through region build. Authored at 5M-5 Phase B. Tier docs reach strong ACTIVE state through Phase 5.5 plus 5.6 plus 6 finalization cycles. Pre-Phase-6 docs may carry DRAFT or v0.X states reflecting active iteration.

Post-cascade architecture gaps scheduling. Three items defer to post-book-processing per pipeline-driven schema discipline. Personal dimension system spec authoring at T1\_Personal\_Dimension\_Spec — astral sub-space for creature training plus garden plus housing, 200-plus creatures, integrity-visible. Solo DLC pre-identification catalog authoring at T1\_Tier\_B\_DLC\_Catalog. MMO regional biography variation system authoring per T1\_Tier\_C\_MMO\_Spec — NPC biographies shift under guild integrity control. T1\_Audio\_Spec plus T1\_UI\_UX\_Spec populate at Phase 6 alongside region build per pipeline consumer demand.

Workflow Sequence

The full project lifecycle workflow, locked April 25, 2026, updated at 5M-5 Phase B with current Phase 5.5 plus 5.6 routing per Strategic Roadmap. Each phase produces deliverables that downstream phases consume. Skipping ahead breaks dependency chains. Phase order is locked.

Open Decisions and Pending Items

Phase 5 cleanup queue closed at 5M-6

Twelve drift items resolved across Phase 5M-5 Phase D, E, F. Closed at Phase F sheet population landings: T0\_Character\_Index CHAR\_NNNN row rename (118 rows CH\_0001 through CH\_0118 renamed to CHAR\_0001 through CHAR\_0118); T0\_Vril\_Site\_Registry Nan Madol row migration (VS\_CHTBD\_PACIFIC\_001 to VS\_CH63\_001 with chapter=63 region=Pohnpei); T0\_Schema\_Dictionary v1.2 MINOR patches per Phase D D-4 plus D-9 secondary findings; T99\_Custom\_Instructions\_Registry v1.0 entries authored (v4.1-Restructure ARCHIVED plus v4.2-Phase-5-Close ACTIVE entries). Closed at Phase E memory cleanup batch: cn0 to nu0 memory ID drift fix confirmed, 5M-prep-era plus 5M-5 Phase A-B drift accumulation consolidated. Closed at Phase D drift resolution batch: T99 cascade-era artifacts implicit-archive verification, HUMANITY parent folder confusion (vestigial Git-sync skeleton), T0\_Schema\_Dictionary doc-type registry exception documentation, T1\_Languages\_and\_Script\_Master singular versus plural naming (no active drift), SQ11 sweep update (stale flag), T1\_Region\_Page\_Template plus T1\_Build\_Pipeline\_Contracts §7 cross-reference alignment, T0\_Source\_Material\_Registry retention confirmed.

Deferred to Phase 6 per pipeline-driven schema discipline

T0\_Source\_Material\_Registry to T0\_Research\_Corpus\_Registry foreign-key column additions defer to Phase 6 region build feedback per Phase D D-1 finding. Pipeline contract iteration triggers schema expansion; absent active pipeline demand, schema stays at minimum-viable.

Renamed registry column expansion

Column expansions for T0\_Creature\_Roster, T0\_Quest\_Seed\_Registry, T0\_RNG\_Drop\_Table, T0\_Cross\_Cultural\_Link\_Graph stage at Phase 6 region page build feedback per pipeline-driven schema principle.

Build pipeline contract iteration closed

T1\_Build\_Pipeline\_Contracts at gdoc 16q2hUknjnMXFrzdXj2yfOYrF-aZ6XuzFxJWzU1IOqj0 ACTIVE v1.0 with all ten pipelines locked. §1 UE5 plus §2 Meshy plus §3 AIVA plus §4 ElevenLabs plus §5 Cinematic Scene Build plus §6 Quest Writing plus §7 Region Page Build plus §8 Book Processing plus §9 Story Spine plus §10 SFX. Iterative per CVD §0 Authority Hierarchy clarification at next contract iteration cycle. Seventeen New T0 Registries canonical reference count (six spawned through pipeline lock plus eleven pre-existing with column expansions per minimum-viable adds).

Naming and content sweeps

T1\_Languages\_and\_Script\_Master singular versus plural Drive filename. Drive uses singular Script; internal title plus reference doc all consistent at singular. No active drift confirmed at Phase D close.

SQ11 sweep update absorbed into T1\_Build\_Pipeline\_Contracts §9 Grid 3 plus T1\_World\_Geography\_Master v2.1 §8 at Phase 5 close.

Recent Architecture Changes

June 29, 2026\. Phase 5.5 plus Phase 5.6 advanced in-repo (Claude Code) post-migration. Phase 5.5 Pre-Spine Cleanup executed — 12 empty T2 ChapterDesign plus ResearchBasis stubs deleted; Tier 2 folder removed. Phase 5.6 T1\_Research\_Corpus\_Master Chunk 5B-2 authored (Ch 75 plus Ch 76 plus Ch 77 plus Prologue plus Epilogue), closing Chunk 5 to full Ch 2-77 plus Prologue plus Epilogue coverage; grounded in CVD plus T0\_Hard\_Lines plus T3\_Core plus T4\_House\_of\_Velheim\_Canonical plus T3\_Familiars\_Named plus T1\_Threads\_22 and fresh-context-critic-verified for the CVD §17.9 plus §18 Grand Sage hard line. Two pre-migration source corruptions repaired as faithful recoveries: Ch 59 Africa Revisit front-half (clean source supplied) and a Ch 69-tail front-truncated bullet (recovered from its intact in-doc parallel). The five endgame canon flags were then adversarially resolved against full canon (per-flag fresh-context review of CVD plus all tier docs plus adjacent chapters plus Pillars 1.12/1.13) and the RCM flipped DRAFT-to-ACTIVE to [ACTIVE v1.1.4]. Registry-fidelity harness ported to /harness/; all 29 T0 registries converted to /registries/ CSV as the live-canon layer; drift-queue ch\_cross appends applied to T0\_Research\_Corpus\_Registry. Story Spine cascade readiness scaffold authored at /docs/SPINE\_CASCADE\_READINESS.md. T1\_RCM roster line updated; broader T1\_AaS roster-refresh (queued since the Wave 4c frame-only patch) remains a separate pass.

May 17, 2026\. HUM-PHASE-5-COMPLETE marker landed Session 5M-6. Phase 5 Restructure closes. Twenty-five sessions across four work streams complete. Canonical state at Phase 5 close captured in HUM-PHASE-5-COMPLETE marker file. Tier 0 thirty entities total (twenty-nine sheets plus Schema\_Dictionary doc), twenty-one at active populate. Tier 1 twenty docs (thirteen ACTIVE plus one ACTIVE single-section plus one DRAFT working plus four DRAFT plus this Architecture doc), six retirements under folder-policy. Tier 99 ten docs (seven ACTIVE plus one DRAFT plus two transitionals retiring at this marker). T99\_Phase\_5\_Closing\_Sequence\_Handoff plus T99\_Pipeline\_Contract\_Buildability\_Audit retired by folder-policy at marker landing (manual Drive UI move to /Humanity/\_Archive/ at folder ID 1IjYxTjAw8E0fr71CejiPFV9VIwTJrXX2). T99\_Phase\_5\_Audit\_Findings Phase G collapsed and trashed pre-marker (audit doc duplicate of canonical ledger held in T1\_AaS plus Schema Dictionary plus CI Registry plus T0 sheets). v4.2-Phase-5-Close custom instructions retire; v5-Operational activates next session covering Phase 5.5 plus 5.6 plus Phase 6 cascade scope. Compaction Discipline applied to this section — twelve prior phase-execution entries roll up into this single HUM-PHASE-5-COMPLETE phase-canonical entry per phase-close compaction protocol.

May 17, 2026\. Session 5M-6 compaction pass. T1\_Architecture\_and\_State v3.0 to v3.1 PATCH. Title block Current focus line updated to Phase 5.5 launch state. Sessions complete section rebuilt to consolidated four-stream summary. Sessions pending section cleared. Open Decisions section compacted with cleanup queue closed plus deferred-to-Phase-6 retention plus build pipeline contract iteration closed entry retained for reference. Recent Architecture Changes section compacted from twelve entries to two phase-canonical entries.

May 17, 2026\. T1\_Architecture\_and\_State v3.1 to v3.2 PATCH. Strategic Roadmap section bullet order corrected from cascade-era Phase 5.5 then Phase 5.6 sequencing to Phase 5.6 finish then Phase 5.5 per user concurrent-execution directive — Phase 5.6 Corpus Doc Rebuild runs concurrent with Phase 5 close per Phase 5.6 chunks 1 through 4A complete state, chunks 4B plus 5 plus absorption verification against T1\_WGM v2.1 region anchors gate Phase 5.5 wholesale T2 archive launch. Workflow Sequence section bullets reordered to match. Title block Current focus line updated to Phase 5.6 chunks 4B plus 5 active state. v5-Operational custom instructions reference corrected Strategic Roadmap order at lock.

May 17, 2026\. Pre-Chunk-5A Cleanup Pass Sessions A through D complete. Phase-canonical roll-up entry per Compaction Discipline. Session A: CVD v1.3 to v1.4 ACTIVE — Ch 67-69 Pohljar plus Tiamarath plus Maatherion canonical names locked, §3 Component 1 Pacific anchor via Tiamarath dual-purpose, §17.7 substrate-tier preservation hard line added. Session B: T1\_World\_Geography\_Master v2.1 to v2.2 ACTIVE — Ch 66-69 canonical region content plus real substrate references via T0\_RC\_NNNNN routing plus Ch 22 CLOSED at §15. Session C Wave 2c: T1\_Languages\_and\_Script\_Master v2.0 to v2.1, T1\_Threads\_22\_Master\_References v2.1 to v2.2 catchup, T1\_Vril\_and\_Magic\_System\_Master v2.1 to v2.2 catchup, T1\_World\_Geography\_Master v2.2 to v2.3 §14.6 residue absorbed. Session C Wave 3 Part 1: T0\_Schema\_Dictionary v1.2 to v1.3 with §2.9 extensions JSON convention plus twelve T1 doc version bumps plus §7 version history rebuild. Session C Wave 3 Part 2: T0\_Chapter\_Index v1.1 to v1.2, T0\_Region\_Index v1.1 to v1.2, T0\_Hard\_Lines v0.1 to v0.2 with batched rename propagation HL\_0054 Maatherion plus HL\_0106 Underwater Sites plus HL\_0066 Wave 2c residue. Session D Wave 4a: T3\_Familiars\_Named DRAFT v0.1 to ACTIVE v1.0 full canonical rewrite at gdoc 1T-H4VbYDl8qR-6Xk4\_lMe0daPowTX7DamPNjljCI85Y. Session D Wave 4b: T3\_Creatures\_Tameable DRAFT v0.1 to ACTIVE v1.0 full canonical rewrite at gdoc 1cvvH2EYfrbrd-k9MD5JEgeeX82z8Cq9CgMNdnE1crRI. Body roster sections in this doc remain at pre-Sessions-A-through-D version references pending separate roster-refresh wave; this roll-up entry captures the canonical Drive state for audit trail completeness.

May 17, 2026\. T1\_Architecture\_and\_State v3.2 to v3.3 PATCH. Pre-Chunk-5A Cleanup Pass Session E Wave 4c applied to this doc. Recent Architecture Changes section append covering Sessions A through D completion state plus T3\_Familiars\_Named v1.0 plus T3\_Creatures\_Tameable v1.0 ACTIVE promotions. Current focus line revised to reflect Pre-Chunk-5A Cleanup Pass mid-execution state plus T1\_World\_Geography\_Master v2.3 region anchor authority. Tier 1 plus Tier 0 plus Tier 3 roster body content unchanged at this patch — body roster refresh queued as separate wave per Wave 4c frame-only scope discipline. Title bracket bumped from v3.2 to v3.3.

Appendix — Architecture Design Rationale

Historical reference. The architecture in this doc was shaped by five research domains integrated during Blueprint v3.0 and v3.1 production in April 2026\. The Agent Skills cross-platform standard provided the three-level progressive disclosure pattern adopted for Tier 0 registry design, dropping token cost meaningfully versus naive always-load. The MMORPG database-oriented design literature, including BitCraft and large-scale MySQL practice, validated structured fields with JSON extensions over ORM magic, junction tables for many-to-many relationships, column-level denormalization where it eliminates high-frequency joins, and schema version discipline as a production requirement. The ConStory consistency taxonomy supplied the error-class framework used in normalization passes, with attention to mid-narrative drift clusters and evidence-grounded flagging.

Curation versus generation. The SkillsBench research finding that human-curated skills outperform self-generated LLM skills by a meaningful margin shaped the workflow split adopted here. Josh authors canon. Claude produces structured form under strict templates. Normalization validates Claude output against Josh's canonical anchors. Claude does not invent canon. The cascade work is curation-guided generation, not pure LLM generation, and the architecture enforces that split through the trust-tier model and the authority hierarchy.

Why this lives as an appendix. The substance above is historical. Current operational discipline is captured in CVD §17 hard lines, T0\_Schema\_Dictionary v1.3 per-registry schema authority, T1\_Build\_Pipeline\_Contracts v1.0 pipeline scope, and the T99\_Normalization\_Protocol. This appendix records what informed the design so future iterations can revisit assumptions without rereading retired Blueprint versions. It is not load-bearing for ongoing work and does not require attention during normal sessions.

Generated by harness/site/structure_site.py — the URL path is the repo path. review root